3 subject="""comment 1"""
4 date="2023-02-16T18:55:06Z"
6 I'm surprised by this behavior change! (And I replicated it on linux, no
7 apologies necessary for also testing Windows support..)
9 [[!commit 826b225ca81d469640e51628865dbd64a1d37773]] is the buggy commit.
10 When there is no metadata log, it accidentially skips calling
13 I've fixed that. I wonder if I should push up the shedule of the next
14 release because of this reversion? Currently I'm inclined to treat it as
15 medium urgency for release (1-2 weeks).